Method and apparatus for cascaded multi-input content preparation templates for 5g networks

ABSTRACT

A method, computer program, and computer system is provided for content preparation for a 5G network. One or more cascaded content preparation processes are identified. Inputs and outputs associated with the identified cascaded content preparation processes are defined based on a content preparation template. A workflow corresponding to the defined inputs and outputs is generated based on two or more of the identified cascaded content preparation processes.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims priority from U.S. Provisional Patent Application No. 63/168,953 (filed Mar. 31, 2021) in the U.S. Patent and Trademark Office, the entirety of which is herein incorporated by reference.

FIELD

This disclosure relates generally to field of data processing, and more particularly to 5G networks.

BACKGROUND

3GPP TS26.512 defines the concept of a content preparation template to set up the processing of the media streams before hosting the content for streaming. It also defines the content hosting configuration for the distribution of the content.

SUMMARY

Embodiments relate to a method, system, and computer readable medium for content preparation for a 5G network. According to one aspect, a method for content preparation for a 5G network is provided. The method may include identifying one or more cascaded content preparation processes. Inputs and outputs associated with the identified cascaded content preparation processes are defined based on a content preparation template. A workflow corresponding to the defined inputs and outputs is generated based on two or more of the identified cascaded content preparation processes.

According to another aspect, a computer system for content preparation for a 5G network is provided. The computer system may include one or more processors, one or more computer-readable memories, one or more computer-readable tangible storage devices, and program instructions stored on at least one of the one or more storage devices for execution by at least one of the one or more processors via at least one of the one or more memories, whereby the computer system is capable of performing a method. The method may include identifying one or more cascaded content preparation processes. Inputs and outputs associated with the identified cascaded content preparation processes are defined based on a content preparation template. A workflow corresponding to the defined inputs and outputs is generated based on two or more of the identified cascaded content preparation processes.

According to yet another aspect, a computer readable medium for content preparation for a 5G network is provided. The computer readable medium may include one or more computer-readable storage devices and program instructions stored on at least one of the one or more tangible storage devices, the program instructions executable by a processor. The program instructions are executable by a processor for performing a method that may accordingly include identifying one or more cascaded content preparation processes. Inputs and outputs associated with the identified cascaded content preparation processes are defined based on a content preparation template. A workflow corresponding to the defined inputs and outputs is generated based on two or more of the identified cascaded content preparation processes.

BRIEF DESCRIPTION OF THE DRAWINGS

These and other objects, features and advantages will become apparent from the following detailed description of illustrative embodiments, which is to be read in connection with the accompanying drawings. The various features of the drawings are not to scale as the illustrations are for clarity in facilitating the understanding of one skilled in the art in conjunction with the detailed description. In the drawings:

FIG. 1 illustrates a networked computer environment according to at least one embodiment;

FIG. 2A is a diagram depicting a system for content preparation before downlink streaming, according to at least one embodiment;

FIG. 2B is a diagram of cascaded content preparation processes with multiple inputs, according to at least one embodiment;

FIG. 3 is an operational flowchart illustrating the steps carried out by a program for content preparation for a 5G network, according to at least one embodiment;

FIG. 4 is a block diagram of internal and external components of computers and servers depicted in FIG. 1 according to at least one embodiment;

FIG. 5 is a block diagram of an illustrative cloud computing environment including the computer system depicted in FIG. 1, according to at least one embodiment; and

FIG. 6 is a block diagram of functional layers of the illustrative cloud computing environment of FIG. 5, according to at least one embodiment.

DETAILED DESCRIPTION

Detailed embodiments of the claimed structures and methods are disclosed herein; however, it can be understood that the disclosed embodiments are merely illustrative of the claimed structures and methods that may be embodied in various forms. Those structures and methods may, however, be embodied in many different forms and should not be construed as limited to the exemplary embodiments set forth herein. Rather, these exemplary embodiments are provided so that this disclosure will be thorough and complete and will fully convey the scope to those skilled in the art. In the description, details of well-known features and techniques may be omitted to avoid unnecessarily obscuring the presented embodiments.

Embodiments relate generally to the field of data processing, and more particularly to 5G networks. The following described exemplary embodiments provide a system, method and computer program for, among other things, content preparation for a 5G network. Therefore, some embodiments have the capacity to improve the field of computing by allowing for defining content preparation as a cascaded series of content preparation processes, each defined by a content preparation template which accepts one or more inputs.

As previously described, 3GPP TS26.512 defines the concept of a content preparation template to set up the processing of the media streams before hosting the content for streaming. It also defines the content hosting configuration for the distribution of the content. The current 5G media streaming architecture defined in 3GPP TS26.501 only defines the general architecture for uplink and downlink media streaming. 3GPP TS26.512 defines the concept of a content preparation template (CPT) to prepare received content for downlink streaming. However, it doesn't define the process for the content miss with content preparation. It may be advantageous, therefore, to define content preparation as a cascaded series of content preparation processes, each defined by a content preparation template which accepts one or more inputs.

A 5G media streaming (5GMS) system may be an assembly of application functions, application servers, and interfaces from the 5G media streaming architecture that support either downlink media streaming services or uplink media streaming services, or both. A 5GMS Application Provider may include a party that interacts with functions of the 5GMS system and supplies a 5GMS Aware Application that interacts with functions of the 5GMS system. The 5GMS Aware Application may refer to an application in the user equipment (UE), provided by the 5GMS Application Provider, that contains the service logic of the 5GMS application service, and interacts with other 5GMS Client and Network functions via the interfaces and application programming interfaces (APIs) defined in the 5GMS architecture. A 5GMS Client may refer to a UE function that is either a 5GMS downlink (5GMSd) Client or a 5GMS uplink (5GMSu) Client, or both.

The 5GMSd Client may refer to a UE function that includes at least a 5G media streaming player and a media session handler for downlink streaming and that may be accessed through well-defined interfaces/APIs. The 5GMSu Client may refer to an originator of a 5GMSu service that may be accessed through well-defined interfaces/APIs. A 5GMSu media streamer may refer to a UE function that enables uplink delivery of streaming media content to an Application Server (AS) function of the 5GMS Application Provider, and which interacts with both the 5GMSu Aware Application for media capture and subsequent streaming, and the Media Session Handler for media session control.

A dynamic policy may refer to a dynamic policy and charging control (PCC) rule for an uplink or downlink application flow during a media session. An egest session may refer to an uplink media streaming session from the 5GMS AS towards the 5GMSu Application Provider. An ingest session may refer to a session to upload the media content to a 5GMSd AS. A policy template may refer to a collection of (semi-static) Policy or Control Function (PCF)/Network Exposure Function (NEF) API parameters which are specific to the 5GMS Application Provider and also the resulting PCC rule. A policy template ID may identify the desired policy template, which is used by the 5GMSd Application Function (AF) to select the appropriate PCF/NEF API towards the 5G system so that the PCF can compile the desired PCC rule. The Media Player Entry may refer to a document or a pointer to a document that defines a media presentation (e.g., a media presentation description (MPD) for DASH or a uniform resource locator (URL) to a video clip file). A Media Streamer Entry may refer to a pointer (e.g., in the form of a URL) that defines an entry point of an uplink media streaming session. A presentation entry may refer to a document or a pointer to a document that defines an application presentation, such as an HTML5 document.

A Provisioning Session may refer to a data structure supplied at an interface (Mid) by a 5GMSd Application provider that configures the 5GMSd features relevant to a set of 5GMSd Aware Applications. A 5GMSd Media Player may refer to a UE function that enables playback and rendering of a media presentation based on a media play entry and exposing some basic controls such as play, pause, seek, stop, to the 5GMSd Aware Application. Server Access Information may refer to a set of parameters and addresses (including 5GMSd AF and 5GMSd AS addresses) which are needed to activate the reception of a streaming session. A Service and Content Discovery may refer to functionality and procedures provided by a 5GMSd Application Provider to a 5GMS Aware Application that enables the end user to discover the available streaming service and content offerings and select a specific service or content item for access. A Service Announcement may refer to procedures conducted between the 5GMS Aware Application and the 5GMS Application Provider such that the 5GMS Aware Application is able to obtain 5GMS Service Access Information, either directly or in the form of a reference to that information.

A third party player may refer to a part of an application that uses APIs to exercise selected 5GMSd functions to play back media content. A third party uplink streamer may refer to a part of an application that uses APIs to exercise selected 5GMSu functions to capture and stream media content

Aspects are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer readable media according to the various embodiments. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer readable program instructions.

Referring now to FIG. 1, a functional block diagram of a networked computer environment illustrating a content preparation system 100 (hereinafter “system”) for content preparation for a 5G network. It should be appreciated that FIG. 1 provides only an illustration of one implementation and does not imply any limitations with regard to the environments in which different embodiments may be implemented. Many modifications to the depicted environments may be made based on design and implementation requirements.

The system 100 may include a computer 102 and a server computer 114. The computer 102 may communicate with the server computer 114 via a communication network 110 (hereinafter “network”). The computer 102 may include a processor 104 and a software program 108 that is stored on a data storage device 106 and is enabled to interface with a user and communicate with the server computer 114. As will be discussed below with reference to FIG. 4 the computer 102 may include internal components 800A and external components 900A, respectively, and the server computer 114 may include internal components 800B and external components 900B, respectively. The computer 102 may be, for example, a mobile device, a telephone, a personal digital assistant, a netbook, a laptop computer, a tablet computer, a desktop computer, or any type of computing devices capable of running a program, accessing a network, and accessing a database.

The server computer 114 may also operate in a cloud computing service model, such as Software as a Service (SaaS), Platform as a Service (PaaS), or Infrastructure as a Service (IaaS), as discussed below with respect to FIGS. 5 and 6. The server computer 114 may also be located in a cloud computing deployment model, such as a private cloud, community cloud, public cloud, or hybrid cloud.

The server computer 114, which may be used for content preparation for a 5G network is enabled to run a Content Preparation Program 116 (hereinafter “program”) that may interact with a database 112. The Content Preparation Program method is explained in more detail below with respect to FIG. 3. In one embodiment, the computer 102 may operate as an input device including a user interface while the program 116 may run primarily on server computer 114. In an alternative embodiment, the program 116 may run primarily on one or more computers 102 while the server computer 114 may be used for processing and storage of data used by the program 116. It should be noted that the program 116 may be a standalone program or may be integrated into a larger content preparation program.

It should be noted, however, that processing for the program 116 may, in some instances be shared amongst the computers 102 and the server computers 114 in any ratio. In another embodiment, the program 116 may operate on more than one computer, server computer, or some combination of computers and server computers, for example, a plurality of computers 102 communicating across the network 110 with a single server computer 114. In another embodiment, for example, the program 116 may operate on a plurality of server computers 114 communicating across the network 110 with a plurality of client computers. Alternatively, the program may operate on a network server communicating across the network with a server and a plurality of client computers.

The network 110 may include wired connections, wireless connections, fiber optic connections, or some combination thereof. In general, the network 110 can be any combination of connections and protocols that will support communications between the computer 102 and the server computer 114. The network 110 may include various types of networks, such as, for example, a local area network (LAN), a wide area network (WAN) such as the Internet, a telecommunication network such as the Public Switched Telephone Network (PSTN), a wireless network, a public switched network, a satellite network, a cellular network (e.g., a fifth generation (5G) network, a long-term evolution (LTE) network, a third generation (3G) network, a code division multiple access (CDMA) network, etc.), a public land mobile network (PLMN), a metropolitan area network (MAN), a private network, an ad hoc network, an intranet, a fiber optic-based network, or the like, and/or a combination of these or other types of networks.

The number and arrangement of devices and networks shown in FIG. 1 are provided as an example. In practice, there may be additional devices and/or networks, fewer devices and/or networks, different devices and/or networks, or differently arranged devices and/or networks than those shown in FIG. 1. Furthermore, two or more devices shown in FIG. 1 may be implemented within a single device, or a single device shown in FIG. 1 may be implemented as multiple, distributed devices. Additionally, or alternatively, a set of devices (e.g., one or more devices) of system 100 may perform one or more functions described as being performed by another set of devices of system 100.

Referring now to FIG. 2A, a diagram 200A of content preparation before downlink streaming is depicted. In a collaboration use case, the 5GMSd Application Provider requests content preparation for its stream before distribution. In a content preparation use-case, the content is provided by the Application Provider through M2d. One option is to pull the content from Application Provider using the HTTP pull-based ingest protocol defined in 3GPP TS 26.512. Then the content is prepared for distribution as defined in the Content Preparation Template (CPT) and last, the distribution happens based on Content Hosting Configuration Template (HCT), both set by the Application Provider.

Each HCT may include one or more CPTs, each defined in its Distribution Configurations. However, the HCT shall include only one Ingest Configurations. Therefore, each input media track needs one CHT and may have one or more CPTs, one for each distribution configuration. A CPT may create one or multiple output tracks.

One most common use-case of multimedia streaming is when there exists one track of the audio and one track of the video. If CPT needs to create a manifest for this content, then the outputs of two CPTs need to be integrated with a single manifest for this audio-visual content.

In a content hosting configuration with multiple ingests, multiple Ingest Configuration (IC) may be enabled for an HCT. To identify them from each other, a unique identifier may be added to each IC. The scope of this uniqueness in the parent HCT. For a content preparation template with multiple inputs, the IC's ids may be added to the content preparation template (CPT). This allows a CPT to have more inputs than one. Therefore, a more complex content preparation can be performed based on multiple inputs. For cascading content preparation outputs, a content preparation's input may be defined as another content preparation's output. This enables cascading multiple content preparation processes and even create a workflow out of two or more content preparation processes. As an example, the input for a content preparation may be defined as the output for another content preparation. To achieve the above, a unique ID may be defined for each input and output of every CPT. Then a CPT input may be defined as another CPT's output. The connection between two CPTs is defined with an Ingest Configuration (IC). Therefore, the HCT may include an IC that is used to connect a CPT's output to another CPT's input.

Referring now to FIG. 2B, a diagram 200B of cascaded content preparation processes with multiple inputs is depicted. Content preparation processes (CPP) CPP1 and CPP2 are used for video and audio processing respectively. Each of these processes may create one or more video/audio outputs that are stored in the cache/storage. For creating a single manifest for the content that describes both audio and video components, a third content preparation process CPP3 is used that received its inputs from the CPP1 and CPP2 and provides its output to the cache/storage.

Each content preparation process is defined by one content preparation template (CPT1, CPT2, and CPT3). CPT3 defines two inputs and its inputs are tied to the CPT1 and CPT2 outputs respectively. CPT3 may create one or more manifests (in different formats such as DASH and HLS, or with different media codes and/or profiles).

The content preparation template's inputs are tied to an ingest or one output of another content preparation template using the assigned ids.

The following Table 1 may show definitions of ContentHostingConfiguration resources:

TABLE 1 Data Property name Type Cardinality Description name String 1 . . . 1 A name for this Content Hosting Configuration. IngestConfiguration Array 1 . . . 1 Describes the 5GMSd Application (Object) Provider's origin server from which media resources will be ingested via interface M2d. id String 1 . . . 1 The unique identifier for this configuration. path String 1 . . . 1 The relative path which will be used to address the media resources at interface M2d. This path is provided by the 5GMSd AF in the case of Push-based ingest. pull Boolean 1 . . . 1 Indicates whether to the 5GMSd AS shall use Pull or Push for ingesting the content. protocol URI 1 . . . 1 A fully-qualified term identifier String allocated in the name space urn:3gpp:5gms:content-protocol that identifies the content ingest protocol. The set of supported protocols is defined in clause 8. entryPoint String 1 . . . 1 An entry point to ingest the content. The semantics of the entry point are dependent on the selected ingest protocol. In the case of Push ingest (pull flag is set to False), this parameter is returned by the 5GMSd AF to the 5GMSd Application Provider and indicates the entry point for pushing the content. In case of Pull (pull flag is set to True), the entryPoint shall be provided to the 5GMSd AF to indicate the location from which content is to be pulled. In this case, the entryPoint shall be used as the base URL. A request received by the 5GMSd AS is mapped to a URL using the provided base URL to fetch the content from the origin server. DistributionConfigurations Array 1 . . . 1 Specifies the distribution method and (Object) configuration for the ingested content. More than one distribution may be configured for the ingested content, e.g. to offer different distribution configurations such as DASH and HLS. ingestId Array 1 . . . 1 The array of IngestConfiguration's (Object) that are used in this distribution configuration. contentPreparation Array 0 . . . 1 Indicates that content preparations (object) prior to distribution is requested by the 5GMSd Application Provider. contentPreparationId String 0 . . . 1 Indicates that content preparation prior to distribution is requested by the 5GMSd Application Provider. It identifies the Content Preparation Template that shall be used as defined in clause 7.4. input Array 1 . . . 1 The array of Content preparation (object) template input which defines the connection for each input. id string 1 . . . 1 This input's ids which each is unique between all inputs id, outputs id, content preparation ids and ingest ids. connectedId string 1 . . . 1 The ingestId or outputId which is connected to this input. OutputId Array 1 . . . 1 The array of Content preparation (string) template output ids which unique between all inputs id, outputs id, content preparation ids and ingest ids. canonicalDomainName String 1 . . . 1 All resources of the current distribution shall be accessible through this default FQDN assigned by the 5GMSd AF. domainNameAlias String 1 . . . 1 The 5GMSd Application Provider may assign another FQDN through which media resources are additionally accessible at M4d. This domain name is used by the 5GMSd AS to select an appropriate Server Certificate to present at M4d, and to set appropriate CORS HTTP response headers at M4d. If this property is present, the 5GMSd Application Provider is responsible for providing in the DNS a CNAME record that resolves domainNameAlias to canonicalDomainName. PathRewriteRules Array 0 . . . 1 An ordered list of rules for rewriting (Object) the request URL paths of media resource requests handled by the 5GMSd AS. If multiple rules match a particular resource's path, only the first matching rule, in order of appearance in this array, shall be applied. requestPathPattern String 1 . . . 1 A regular expression against which the path part of each 5GMSd AS request URL, including the leading “/”, and up to and including the final “/”, shall be compared. (Any leaf path element following the final “/” shall be excluded from this comparison.) In the case of Pull-based ingest, the M4d download request path is used in the comparison. In the case of Push-based ingest, the M2d upload request path is used in the comparison. In either case, if the request path matches this pattern, the path mapping specified in the corresponding mappedPath shall be applied. mappedPath String 1 . . . 1 A replacement for the portion of the 5GMSd AS request path that matches requestPathPattern. In the case of Pull-based ingest, IngestConfiguration.entryPoint is concatenated with the mapped path and any leaf path element from the original M4d download request to form the M2d origin request URL. In the case of Push-based ingest, canonicalDomainName (and, optionally, domainNameAlias) are concatenated with the mapped path and any leaf path element from the original M2d upload request to form the distribution URL(s) exposed over M4d. CachingConfigurations Array 0 . . . 1 Defines a configuration of the (Object) 5GMSd AS cache for a matching subset of media resources ingested in relation to this Content Hosting Configuration. urlPatternFilter String 1 . . . 1 A pattern that will be used to match media resource URLs to determine whether a given media resource is eligible for caching by the 5GMSd AS. The format of the pattern shall be a regular expression. CachingDirectives Object 1 . . . 1 If a urlPatternFilter applies to a resource, then the provided CachingDirectives shall be applied by the 5GMSd AS at M4d, potentially overwriting any origin caching directives ingested at M2d. statusCodeFilters Array 0 . . . 1 The set of HTTP origin response (integer) status codes to which these CachingDirectives apply. The filter shall be provided as a regular expression. If the list is empty, the CachingDirectives shall apply to all HTTP origin response status codes at M2d. noCache Boolean 1 . . . 1 If set to True, this indicates that the media resources matching the filters shall not be cached by the 5GMSd AS and shall be marked as not to be cached when served by the 5GMSd AS at M4d. maxAge Integer 0 . . . 1 The caching time-to-live period that shall be set on ingested media resources matching the filters. This determines the minimum period for which the 5GMSd AS shall cache matching media resources as well as the time-to-live period signalled by the 5GMSd AS at interface M4d when it serves such media resources. The time-to-live for a given media resource shall be calculated relative to the time it was ingested. GeoFencing Object 0 . . . N Limit access to the content to the indicated geographic areas. locatorType URI 1 . . . 1 The type of the locators shall be String indicated using a fully-qualified term identifier URI from the controlled vocabulary urn:3gpp:5gms:locator-type, as specified in clause 7.6.4.6, or else from a vendor-specific vocabulary. locators Array 1 . . . 1 Array of locators from which access (String) to the resources is to be allowed. The format of the locator strings shall be determined by the value of locatorType, as specified in clause 7.6.4.6. UrlSignature Object 0 . . . 1 Defines the URL signing scheme. Only correctly signed and valid URLs will be allowed to access the content resource at M4d. urlPattern String 1 . . . 1 A pattern that shall be used to match M4d media resource URLs. The 5GMSd AS shall not serve a matching media resource at M4d unless it includes a valid authentication token. The format of the pattern shall be a regular expression. tokenName String 1 . . . 1 The name of the M4d request query parameter that the Media Player should use to present the authentication token when required to do so. passphraseName String 1 . . . 1 The name of the query parameter that is used to refer to the passphrase when constructing the authentication token. Note that the token is not included in the cleartext part of the M4d URL query component. passphrase String 1 . . . 1 The shared secret between the 5GMSd Application Provider and the 5GMSd AS for this DistributionConfiguration. The passphrase is used in the computation and verification of the M4d authentication token but is never sent in-the-clear over that interface. tokenExpiryName String 1 . . . 1 The name of the M4d request query parameter that the Media Player should use to present the token expiry field. useIPAddress Boolean 1 . . . 1 If set to True, the IP address of the UE is included in the computation of the authentication token for resources that match urlPattern and access to matching media resources shall be allowed by the 5GMSd AF only when the M4d request is made from a UE with this IP address. ipAddressName String 0 . . . 1 The name of the M4d request query parameter that is encoded as part of the authentication token if the useIPAddress flag is set to True. Note that the IP address is not passed in the cleartext part of the M4d URL query component. certificateId String 0 . . . 1 When content is distributed using TLS, the X.509 certificate for the origin domain is shared with the 5GMSd AF so that it can be presented by the 5GMSd AS in the TLS handshake at M4d. This attribute indicates the identifier of the certificate to use.

Referring now to FIG. 3, an operational flowchart illustrating the steps of a method 300 carried out by a program for content preparation for a 5G network is depicted.

At 302, the method 300 may include identifying one or more cascaded content preparation processes.

At 304, the method 300 may include defining inputs and outputs associated with the identified cascaded content preparation processes based on a content preparation template.

At 306, the method 300 may include generating a workflow corresponding to the defined inputs and outputs based on two or more of the identified cascaded content preparation processes.

It may be appreciated that FIG. 3 provides only an illustration of one implementation and does not imply any limitations with regard to how different embodiments may be implemented. Many modifications to the depicted environments may be made based on design and implementation requirements.

FIG. 4 is a block diagram 400 of internal and external components of computers depicted in FIG. 1 in accordance with an illustrative embodiment. It should be appreciated that FIG. 4 provides only an illustration of one implementation and does not imply any limitations with regard to the environments in which different embodiments may be implemented. Many modifications to the depicted environments may be made based on design and implementation requirements.

Computer 102 (FIG. 1) and server computer 114 (FIG. 1) may include respective sets of internal components 800A,B and external components 900A,B illustrated in FIG. 5. Each of the sets of internal components 800 include one or more processors 820, one or more computer-readable RAMs 822 and one or more computer-readable ROMs 824 on one or more buses 826, one or more operating systems 828, and one or more computer-readable tangible storage devices 830.

Processor 820 is implemented in hardware, firmware, or a combination of hardware and software. Processor 820 is a central processing unit (CPU), a graphics processing unit (GPU), an accelerated processing unit (APU), a microprocessor, a microcontroller, a digital signal processor (DSP), a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), or another type of processing component. In some implementations, processor 820 includes one or more processors capable of being programmed to perform a function. Bus 826 includes a component that permits communication among the internal components 800A,B.

The one or more operating systems 828, the software program 108 (FIG. 1) and the Content Preparation Program 116 (FIG. 1) on server computer 114 (FIG. 1) are stored on one or more of the respective computer-readable tangible storage devices 830 for execution by one or more of the respective processors 820 via one or more of the respective RAMs 822 (which typically include cache memory). In the embodiment illustrated in FIG. 4, each of the computer-readable tangible storage devices 830 is a magnetic disk storage device of an internal hard drive. Alternatively, each of the computer-readable tangible storage devices 830 is a semiconductor storage device such as ROM 824, EPROM, flash memory, an optical disk, a magneto-optic disk, a solid state disk, a compact disc (CD), a digital versatile disc (DVD), a floppy disk, a cartridge, a magnetic tape, and/or another type of non-transitory computer-readable tangible storage device that can store a computer program and digital information.

Each set of internal components 800A,B also includes a R/W drive or interface 832 to read from and write to one or more portable computer-readable tangible storage devices 936 such as a CD-ROM, DVD, memory stick, magnetic tape, magnetic disk, optical disk or semiconductor storage device. A software program, such as the software program 108 (FIG. 1) and the Content Preparation Program 116 (FIG. 1) can be stored on one or more of the respective portable computer-readable tangible storage devices 936, read via the respective R/W drive or interface 832 and loaded into the respective hard drive 830.

Each set of internal components 800A,B also includes network adapters or interfaces 836 such as a TCP/IP adapter cards; wireless Wi-Fi interface cards; or 3G, 4G, or 5G wireless interface cards or other wired or wireless communication links. The software program 108 (FIG. 1) and the Content Preparation Program 116 (FIG. 1) on the server computer 114 (FIG. 1) can be downloaded to the computer 102 (FIG. 1) and server computer 114 from an external computer via a network (for example, the Internet, a local area network or other, wide area network) and respective network adapters or interfaces 836. From the network adapters or interfaces 836, the software program 108 and the Content Preparation Program 116 on the server computer 114 are loaded into the respective hard drive 830. The network may comprise copper wires, optical fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers.

Each of the sets of external components 900A,B can include a computer display monitor 920, a keyboard 930, and a computer mouse 934. External components 900A,B can also include touch screens, virtual keyboards, touch pads, pointing devices, and other human interface devices. Each of the sets of internal components 800A,B also includes device drivers 840 to interface to computer display monitor 920, keyboard 930 and computer mouse 934. The device drivers 840, R/W drive or interface 832 and network adapter or interface 836 comprise hardware and software (stored in storage device 830 and/or ROM 824).

It is understood in advance that although this disclosure includes a detailed description on cloud computing, implementation of the teachings recited herein are not limited to a cloud computing environment. Rather, some embodiments are capable of being implemented in conjunction with any other type of computing environment now known or later developed.

Cloud computing is a model of service delivery for enabling convenient, on-demand network access to a shared pool of configurable computing resources (e.g. networks, network bandwidth, servers, processing, memory, storage, applications, virtual machines, and services) that can be rapidly provisioned and released with minimal management effort or interaction with a provider of the service. This cloud model may include at least five characteristics, at least three service models, and at least four deployment models.

Characteristics are as follows:

On-demand self-service: a cloud consumer can unilaterally provision computing capabilities, such as server time and network storage, as needed automatically without requiring human interaction with the service's provider.

Broad network access: capabilities are available over a network and accessed through standard mechanisms that promote use by heterogeneous thin or thick client platforms (e.g., mobile phones, laptops, and PDAs).

Resource pooling: the provider's computing resources are pooled to serve multiple consumers using a multi-tenant model, with different physical and virtual resources dynamically assigned and reassigned according to demand. There is a sense of location independence in that the consumer generally has no control or knowledge over the exact location of the provided resources but may be able to specify location at a higher level of abstraction (e.g., country, state, or datacenter).

Rapid elasticity: capabilities can be rapidly and elastically provisioned, in some cases automatically, to quickly scale out and rapidly released to quickly scale in. To the consumer, the capabilities available for provisioning often appear to be unlimited and can be purchased in any quantity at any time.

Measured service: cloud systems automatically control and optimize resource use by leveraging a metering capability at some level of abstraction appropriate to the type of service (e.g., storage, processing, bandwidth, and active user accounts). Resource usage can be monitored, controlled, and reported providing transparency for both the provider and consumer of the utilized service.

Service Models are as follows:

Software as a Service (SaaS): the capability provided to the consumer is to use the provider's applications running on a cloud infrastructure. The applications are accessible from various client devices through a thin client interface such as a web browser (e.g., web-based e-mail). The consumer does not manage or control the underlying cloud infrastructure including network, servers, operating systems, storage, or even individual application capabilities, with the possible exception of limited user-specific application configuration settings.

Platform as a Service (PaaS): the capability provided to the consumer is to deploy onto the cloud infrastructure consumer-created or acquired applications created using programming languages and tools supported by the provider. The consumer does not manage or control the underlying cloud infrastructure including networks, servers, operating systems, or storage, but has control over the deployed applications and possibly application hosting environment configurations.

Infrastructure as a Service (IaaS): the capability provided to the consumer is to provision processing, storage, networks, and other fundamental computing resources where the consumer is able to deploy and run arbitrary software, which can include operating systems and applications. The consumer does not manage or control the underlying cloud infrastructure but has control over operating systems, storage, deployed applications, and possibly limited control of select networking components (e.g., host firewalls).

Deployment Models are as follows:

Private cloud: the cloud infrastructure is operated solely for an organization. It may be managed by the organization or a third party and may exist on-premises or off-premises.

Community cloud: the cloud infrastructure is shared by several organizations and supports a specific community that has shared concerns (e.g., mission, security requirements, policy, and compliance considerations). It may be managed by the organizations or a third party and may exist on-premises or off-premises.

Public cloud: the cloud infrastructure is made available to the general public or a large industry group and is owned by an organization selling cloud services.

Hybrid cloud: the cloud infrastructure is a composition of two or more clouds (private, community, or public) that remain unique entities but are bound together by standardized or proprietary technology that enables data and application portability (e.g., cloud bursting for load-balancing between clouds).

A cloud computing environment is service oriented with a focus on statelessness, low coupling, modularity, and semantic interoperability. At the heart of cloud computing is an infrastructure comprising a network of interconnected nodes.

Referring to FIG. 5, illustrative cloud computing environment 500 is depicted. As shown, cloud computing environment 500 comprises one or more cloud computing nodes 10 with which local computing devices used by cloud consumers, such as, for example, personal digital assistant (PDA) or cellular telephone 54A, desktop computer 54B, laptop computer 54C, and/or automobile computer system 54N may communicate. Cloud computing nodes 10 may communicate with one another. They may be grouped (not shown) physically or virtually, in one or more networks, such as Private, Community, Public, or Hybrid clouds as described hereinabove, or a combination thereof. This allows cloud computing environment 500 to offer infrastructure, platforms and/or software as services for which a cloud consumer does not need to maintain resources on a local computing device. It is understood that the types of computing devices 54A-N shown in FIG. 5 are intended to be illustrative only and that cloud computing nodes 10 and cloud computing environment 500 can communicate with any type of computerized device over any type of network and/or network addressable connection (e.g., using a web browser).

Referring to FIG. 6, a set of functional abstraction layers 600 provided by cloud computing environment 500 (FIG. 5) is shown. It should be understood in advance that the components, layers, and functions shown in FIG. 6 are intended to be illustrative only and embodiments are not limited thereto. As depicted, the following layers and corresponding functions are provided:

Hardware and software layer 60 includes hardware and software components. Examples of hardware components include: mainframes 61; RISC (Reduced Instruction Set Computer) architecture based servers 62; servers 63; blade servers 64; storage devices 65; and networks and networking components 66. In some embodiments, software components include network application server software 67 and database software 68.

Virtualization layer 70 provides an abstraction layer from which the following examples of virtual entities may be provided: virtual servers 71; virtual storage 72; virtual networks 73, including virtual private networks; virtual applications and operating systems 74; and virtual clients 75.

In one example, management layer 80 may provide the functions described below. Resource provisioning 81 provides dynamic procurement of computing resources and other resources that are utilized to perform tasks within the cloud computing environment. Metering and Pricing 82 provide cost tracking as resources are utilized within the cloud computing environment, and billing or invoicing for consumption of these resources. In one example, these resources may comprise application software licenses. Security provides identity verification for cloud consumers and tasks, as well as protection for data and other resources. User portal 83 provides access to the cloud computing environment for consumers and system administrators. Service level management 84 provides cloud computing resource allocation and management such that required service levels are met. Service Level Agreement (SLA) planning and fulfillment 85 provide pre-arrangement for, and procurement of, cloud computing resources for which a future requirement is anticipated in accordance with an SLA.

Workloads layer 90 provides examples of functionality for which the cloud computing environment may be utilized. Examples of workloads and functions which may be provided from this layer include: mapping and navigation 91; software development and lifecycle management 92; virtual classroom education delivery 93; data analytics processing 94; transaction processing 95; and Content Preparation 96. Content Preparation 96 may define content preparation as a cascaded series of content preparation processes, each defined by a content preparation template which accepts one or more inputs.

Some embodiments may relate to a system, a method, and/or a computer readable medium at any possible technical detail level of integration. The computer readable medium may include a computer-readable non-transitory storage medium (or media) having computer readable program instructions thereon for causing a processor to carry out operations.

The computer readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. A computer readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.

Computer readable program instructions described herein can be downloaded to respective computing/processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and/or a wireless network. The network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. A network adapter card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing/processing device.

Computer readable program code/instructions for carrying out operations may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, configuration data for integrated circuitry, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C++, or the like, and procedural programming languages, such as the “C” programming language or similar programming languages. The computer readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects or operations.

These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks.

The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.

The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer readable media according to various embodiments. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). The method, computer system, and computer readable medium may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in the Figures. In some alternative implementations, the functions noted in the blocks may occur out of the order noted in the Figures. For example, two blocks shown in succession may, in fact, be executed concurrently or substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts or carry out combinations of special purpose hardware and computer instructions.

It will be apparent that systems and/or methods, described herein, may be implemented in different forms of hardware, firmware, or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and/or methods is not limiting of the implementations. Thus, the operation and behavior of the systems and/or methods were described herein without reference to specific software code—it being understood that software and hardware may be designed to implement the systems and/or methods based on the description herein.

No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” are intended to include one or more items, and may be used interchangeably with “one or more.” Furthermore, as used herein, the term “set” is intended to include one or more items (e.g., related items, unrelated items, a combination of related and unrelated items, etc.), and may be used interchangeably with “one or more.” Where only one item is intended, the term “one” or similar language is used. Also, as used herein, the terms “has,” “have,” “having,” or the like are intended to be open-ended terms. Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise.

The descriptions of the various aspects and embodiments have been presented for purposes of illustration, but are not intended to be exhaustive or limited to the embodiments disclosed. Even though combinations of features are recited in the claims and/or disclosed in the specification, these combinations are not intended to limit the disclosure of possible implementations. In fact, many of these features may be combined in ways not specifically recited in the claims and/or disclosed in the specification. Although each dependent claim listed below may directly depend on only one claim, the disclosure of possible implementations includes each dependent claim in combination with every other claim in the claim set. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope of the described embodiments. The terminology used herein was chosen to best explain the principles of the embodiments, the practical application or technical improvement over technologies found in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein. 

What is claimed is:
 1. A method of content preparation for a 5G network, executable by a processor, comprising: identifying one or more cascaded content preparation processes; defining inputs and outputs associated with the identified cascaded content preparation processes based on a content preparation template; and generating a workflow corresponding to the defined inputs and outputs based on two or more of the identified cascaded content preparation processes.
 2. The method of claim 1, wherein unique identifiers correspond to each of the inputs and the outputs.
 3. The method of claim 1, wherein the inputs are defined by an ingest configuration having a defined address and protocols.
 4. The method of claim 1, wherein the outputs are defined by an ingest configuration having a defined address and protocols.
 5. The method of claim 1, further comprising processing one or more audio and video inputs from among the inputs by a content preparation process from among the identified cascaded content preparation processes.
 6. The method of claim 5, further comprising generating a manifest for audiovisual content based on providing audio and video outputs associated with the one or more audio and video inputs to a content preparation process from among the identified cascaded content preparation processes.
 7. The method of claim 6, wherein the audio and video outputs correspond to different formats, different media codecs, or different profiles than the audio and video inputs.
 8. A computer system for content preparation for a 5G network, the computer system comprising: one or more computer-readable non-transitory storage media configured to store computer program code; and one or more computer processors configured to access said computer program code and operate as instructed by said computer program code, said computer program code including: identifying code configured to cause the one or more computer processors to identify one or more cascaded content preparation processes; defining code configured to cause the one or more computer processors to define inputs and outputs associated with the identified cascaded content preparation processes based on a content preparation template; and generating code configured to cause the one or more computer processors to generate a workflow corresponding to the defined inputs and outputs based on two or more of the identified cascaded content preparation processes.
 9. The computer system of claim 8, wherein unique identifiers correspond to each of the inputs and the outputs.
 10. The computer system of claim 8, wherein the inputs are defined by an ingest configuration having a defined address and protocols.
 11. The computer system of claim 8, wherein the outputs are defined by an ingest configuration having a defined address and protocols.
 12. The computer system of claim 8, further comprising processing code configured to cause the one or more computer processors to process one or more audio and video inputs from among the inputs by a content preparation process from among the identified cascaded content preparation processes.
 13. The computer system of claim 12, further comprising generating code configured to cause the one or more computer processors to generate a manifest for audiovisual content based on providing audio and video outputs associated with the one or more audio and video inputs to a content preparation process from among the identified cascaded content preparation processes.
 14. The computer system of claim 13, wherein the audio and video outputs correspond to different formats, different media codecs, or different profiles than the audio and video inputs.
 15. A non-transitory computer readable medium having stored thereon a computer program for content preparation for a 5G network, the computer program configured to cause one or more computer processors to: identify one or more cascaded content preparation processes; defining code configured to cause the one or more computer processors to define inputs and outputs associated with the identified cascaded content preparation processes based on a content preparation template; and generating code configured to cause the one or more computer processors to generate a workflow corresponding to the defined inputs and outputs based on two or more of the identified cascaded content preparation processes.
 16. The computer readable medium of claim 15, wherein unique identifiers correspond to each of the inputs and the outputs.
 17. The computer readable medium of claim 15, wherein the inputs are defined by an ingest configuration having a defined address and protocols.
 18. The computer readable medium of claim 15, wherein the outputs are defined by an ingest configuration having a defined address and protocols.
 19. The computer readable medium of claim 15, wherein the computer program is further configured to cause one or more computer processors to process one or more audio and video inputs from among the inputs by a content preparation process from among the identified cascaded content preparation processes.
 20. The computer readable medium of claim 19, wherein the computer program is further configured to cause one or more computer processors to generate a manifest for audiovisual content based on providing audio and video outputs associated with the one or more audio and video inputs to a content preparation process from among the identified cascaded content preparation processes. 